SCS Events

Event Template Editor - Settings Tab

The settings tab covers general settings for the entire event template.  The scope of these items exceeds any one given component.  There are a few settings groupings as defined below.  

 

General

The general settings block allows you to:

 

- Supply a URL to your custom (if available) help system for overall help with the event

- Customize the tab title which shows up when you run the event

- Reset various settings and UI elements to their defaults.

 

 

 

 

 

 

 

 

 

 

 

Diagnostics

During the run of the event lots of system logs are generated to document what is occurring inside the event.  Some log entries are more important than others, eg an Output reporting an error is more important than knowing that someone has left the event.  These logs can be displayed on the UI so the users participating in the event can see them in real time.  

If you don't want to see logs you can hide the window completely by unchecking the Show the Diagnostics Log window checkbox.

All times in SCS are recorded and conveyed in UTC, however if you would prefer to view the timestamps in your local time zone you can uncheck the Default to UTC checkbox. This does NOT change how the timestamps are recorded (remains UTC) only how the log window displays them on your browser for THIS event.

 

You can also filter the level of information you want to receive.  If you only care about warnings and problems set the level to Warnings.  If you want to get as much of the log as you possibly can choose Verbose.  Note this has no impact on what is actually logged, only what is displayed on the UI.

 

 

 

Location Rights

Events in the modern SCS framework are web based.  As such Events allow users to participate in the same event from all over the ship, even from shore should you choose to allow this.  The idea being that sometimes the bridge, the back deck, those in the lab and so forth all have their part to play in a more complicated Event (like during a trawl).  Rather than one person monitoring a radio waiting around and clicking buttons for everyone else v5 Events allow users to simultaneously participate in the same event instance. 

 

There are two settings which can impact this:

 

  1. Template Permission Level - If the template itself is locked down then the user may not be able to start, join or interact with it.
  2. The Location Rights setting inside the Event template itself can further restrict participation by remote users.

 

 

 

The Location Rights block allows you to regulate how users can participate in running events. 

 

The ability to view and start Event templates / data is restricted via the template permissions themselves (see (1) above).

 

 

Customizing Your Browser Title

In the Settings tab you now have a Custom Browser Title text box.  Leave this blank to use the default naming convention for your browser tab (includes the name of the event being run).  If you enter anything in here it will override the default tab text with whatever you specify.

It might be confusing at first but you can also dynamically link Meta Item values into the title text by typing the name of the meta item you want inside curly brackets. For example, if you entered Custom Title  - {NAME_OF_METAITEM_HERE} then the title would start with Custom Title - followed by whatever the current value is of the Meta Item named 'NAME_OF_METAITEM_HERE'.

 

So take a demo template with 2 Meta Items of interest (Collection Number and Trap Number)

 

 

and a Custom Title of Collection #{Collection Number} | Trap #{Trap Number}

 

 

 

When the event is run you'll notice the title is changed to match your 'custom title' and all Meta Item names inside brackets are replaced by their current value.  If a Meta Item of interest changes (e.g. someone clicks a button which makes the Trap Number increment to 3) then the title will automatically change on everyone's screens as well to reflect the new value.

So in our example, looking at Collection #{Collection Number} | Trap #{Trap Number} we have two Meta Item references - {Collection Number} and {Trap Number}.  When the event is run, these two placeholders will be replaced with their respective values (SCS will determine the current value of the Meta Item named 'Collection Number' and replace the entire {Collection Number} text in the title with the Meta Item's  current value, etc).

 

SCSv5                                                                                                        Page 1 of 1